The Edit Control tab in the Activity Proxy Properties step allows you to determine what the property box will look like and how the user will interact with it in the Workflow Designer. The options in this tab change depending on the property type of the property selected in the left-hand column.
If your property is a string, you can configure the property box to contain a text box or a page range box. Show me what the Edit Control tab looks like for a string property.
Note: If you assign more than one of the following type tags to your token, this order will be used to determine how the token will be evaluated: string, character, date time, time, date, integer, long integer, short integer, number, and Boolean. Only the tag that appears closest to the start of this list will be respected when evaluating conditions.
Example: The property you are configuring should have an integer value, so you only want tokens with numerical values to appear in the token menu. You select Integer, Number, Long Integer and Short Integer in the Token Menu Configuration dialog box.
Note: Besides the type tags listed in the Token Tags section, there are also descriptor tags, such as ID and User. These descriptors also help place your new token on the appropriate token menus, but they will not affect how your token is evaluated in conditions.
If your property is an integral numeric type (Integer, Short, Long, Byte, Unsigned Integer, Unsigned Long, Unsigned Short, or Signed Byte), you can configure the property box to have a spin control or text box. You can also set maximum and minimum amounts for the number. Show me what the Edit Control tab looks like for an integral numeric property.
Example: If you type 10 next to Increment here, when a user clicks the up or down arrows in the activity's property box, the amount will increase or decrease by 10.
Note: If you assign more than one of the following type tags to your token, this order will be used to determine how the token will be evaluated: string, character, date time, time, date, integer, long integer, short integer, number, and Boolean. Only the tag that appears closest to the start of this list will be respected when evaluating conditions.
Note: Besides the type tags listed in the Token Tags section, there are also descriptor tags, such as ID and User. These descriptors also help place your new token on the appropriate token menus, but they will not affect how your token is evaluated in conditions.
If your property is an enumeration, you can choose to have the property box display radio buttons or a drop-down list. Show me what the Edit Control tab looks like for an enumeration property.
When defining an enumeration, you can add the FlagsAttribue to the enumeration to turn it into a flagged enumeration. Flagged enumerations allow you to select more than one enumeration value at once. If your property is a flagged enumeration, you can choose to have the property box display checkboxes or a drop-down list. Show me what the Edit Control tab looks like for a flagged enumeration property.
If your property is a Boolean, you can choose to have the property box display a checkbox or two radio buttons. Show me what the Edit Control tab looks like for a Boolean property.
If your property is a decimal numeric type (Float/Singe, Double, or Decimal), the property box will have a text box that can support tokens and that can have a minimum and/or maximum value. Show me what the Edit Control tab looks like for a decimal property.
Note: If you assign more than one of the following type tags to your token, this order will be used to determine how the token will be evaluated: string, character, date time, time, date, integer, long integer, short integer, number, and Boolean. Only the tag that appears closest to the start of this list will be respected when evaluating conditions.
Note: Besides the type tags listed in the Token Tags section, there are also descriptor tags, such as ID and User. These descriptors also help place your new token on the appropriate token menus, but they will not affect how your token is evaluated in conditions.
If you selected the Make this property reference another activity’s property instead of requiring its own value option in the Advanced tab, the property will have an edit control that allows you to link to another activity's property regardless of the property’s type.
The user can select any custom activity's property that is of the same type and that has the Allow other activities to reference this property option selected in the Advanced tab. You can configure the following options for this control.
Example: If this property box references the annotations created by other activities, you might type "Annotation" here. Show me where the word "Annotation" will appear.
If your property is not one of the above types, and if you did not select the option Make this property reference another activity’s property instead of requiring its own value from the Advanced tab, you can select a custom edit control. Show me what the Edit Control tab looks like for a custom edit control.
Note: This option may have a different name if your property has a type converter or an edit control associated with it. If your property has a type converter, then selecting this option will use the type converter by default. If your property has an edit control, then it will use the edit control by default.
Note: For your edit control to appear in the list, it must inherit from the base class Laserfiche.UI.EditPanel.EditPanelControlBase.
This documentation is specific to version 9.0. You can find the most up-to-date help files for the latest version at Current Online Laserfiche Product Help Files. For further help or feedback, please see the Laserfiche Support Site. |
© 2013 Laserfiche |